Skip to content

feat: migrate deployment to zad-actions#152

Open
anneschuth wants to merge 1 commit intomainfrom
feat/migrate-to-zad-actions
Open

feat: migrate deployment to zad-actions#152
anneschuth wants to merge 1 commit intomainfrom
feat/migrate-to-zad-actions

Conversation

@anneschuth
Copy link
Member

Summary

Migrate the deployment from GitOps-based approach to direct API-based deployment using RijksICTGilde/zad-actions.

Changes:

  • Remove ai-validation-infra repository checkout and sed commands
  • Use zad-actions/deploy action for direct deployment to ZAD Operations Manager
  • Add concurrency control to prevent overlapping deployments

ZAD Configuration:

Project Deployment Component
tr-dev main component-1

Required Setup

Before merging, add the following secret to this repository:

Secret Purpose How to obtain
ZAD_API_KEY ZAD Operations Manager API authentication Request from RIG-cluster team or self-service portal

Post-merge cleanup

After verifying the new deployment works:

  • The GH_PAT secret is no longer needed for this workflow and can be removed

Notes

  • This is a pure migration - same trigger (workflow_dispatch), simpler deployment mechanism
  • The workflow now uses environment variables for ZAD configuration, making it easy to update if needed

Documentation

Replace GitOps-based deployment with direct API-based deployment
using RijksICTGilde/zad-actions.

Changes:
- Remove ai-validation-infra repository checkout and sed commands
- Use zad-actions/deploy action for direct deployment
- Map to tr-dev ZAD project with 'main' deployment
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant